iBank - a Web Interface for the ATM Central Server

In this example the iBank web front end interacts with the ATM Central Server (atmcs), which further relays transaction requests to individual banks.  The interface design follows the object factory pattern.  This example demonstrates how to: This server must be used together with the ATM Central Server (interface layer) and the  Bank Server.  Together with web clients, they form a four-tier software system.


Source Files

Batch Files

Running the Codes

This example was developed under VisiBroker (link) and Apache web server with JServ servlet engine (link).  To run the servlet, you need to set up the JServ servlet engine correctly. (Click here for details.)

After the set up is complete, make sure Apache is running with "net start" (otherwise do "net start apache").  Then point your web browser to http://localhost/ooda/ (note the trailing slash!).  Try the demo sevlet "Counter" to see if the servlet engine is really working.  Proceed only if it works.  If not, it means your configuration for JServ is problematic.

Before you can invoke the iBank application, you need to bring up both the bank server and the atmcs-i server (we use only the interface layer of atmcs to keep things simple).  This involves three steps (since this is a four-tier application, all tiers must be running):
 

  1. cd to the studies/bank directory and do:

  2.     start runsrv
  3. After the server is up, do:

  4.     client localhost test1.txt
    This populates the bank server with some account informatoin.
  5. cd to  the studies/atmcs-i directory and do:

  6.     start runsrv
    After the server is up, you may invoke ibank from http://localhost/ooda/.  To login, use "John" as username and "999" as password.